Prizm Content Connect
Linux Installation
Getting Started with PCC > Installation > Linux > Linux Installation

Prizm Content Connect (PCC) installation is designed to be very straightforward for Linux environments. Follow the steps provided in this section.

Some steps may be specific to a particular Linux distribution; these steps will be labeled as being specific to one of the following: 

The hash sign (#) is used to represent the command prompt. Do not include it when entering the commands.

Make sure you log in as root to the machine.

Step 1 - Download Prizm Content Connect (PCC)

Before you download PCC, note that packages are only available for 64-bit systems.

Before downloading PCC, you will need to purchase a license key or request a Trial Evaluation by filling out the following form: www.accusoft.com/products/prizm-content-connect-pcc/get-self-hosted/.

Once you have purchased a license key or filled out the form for a Trial Evaluation, you can download PCC by:

  1. Following the link provided in the response email and selecting the desired Linux Distribution.

OR

  1. Downloading directly to the Linux server using the 'wget' command for the specific distribution as shown below:

Red Hat, Fedora, CentOS, and Older Linux Distributions

Example
Copy Code 
wget http://products.accusoft.com/PCC/<version>/prizmcc_<version>.x86_64.rpm.tar.gz

Debian and Ubuntu Linux Distributions

Example
Copy Code 
wget http://products.accusoft.com/PCC/<version>/prizmcc_<version>.amd64.deb.tar.gz

Generic .tar.gz Distribution

Example
Copy Code 
wget http://products.accusoft.com/PCC/<version>/prizmcc_<version>.x86_64.tar.gz

For license, fill out the form at http://www.accusoft.com/products/prizm-content-connect-pcc/get-self-hosted/ or http://www.accusoft.com/contact/.

 

Step 2 - Unpack & Install the Downloaded Archive

Open a command line and change to the location where you downloaded the tarball. Use the following command line examples appropriate for your distribution to:

  1. Decompress and unpack the downloaded file. After you have unpacked the archive, the contents will have been decompressed into a directory named "prizmcc_<version>_rpm(or _deb)". 
  2. Change to the unpacked directory and install the packages.

Red Hat, Fedora, CentOS, and Older Linux Distributions

The following example is for Red Hat, Fedora, CentOS, and older Linux distributions:

Example
Copy Code 
# tar –xzvf prizmcc_<version>_rpm.tar.gz
 # cd prizmcc<version>_rpm
 # yum install --nogpgcheck *.rpm

Note: For CentOS 5.x, the following additional dependencies must be installed prior to PCC RPM installation:

  • openjpeg-libs-1.3-7.el5.x86_64.rpm
  • pixman-0.22.0-2.2.el5_10.x86_64.rpm

The Prizm installer does not install them automatically. Please download and install them manually using --nogpgcheck flag as follows:

Example
Copy Code 
# yum install --nogpgcheck ./openjpeg-libs-1.3-7.el5.x86_64.rpm
# yum install --nogpgcheck ./pixman-0.22.0-2.2.el5_10.x86_64.rpm

Debian (Ubuntu) Linux Distributions

The following example is for Debian (Ubuntu) Linux distributions:

Example
Copy Code 
# tar –xzvf prizmcc_<version>_deb.tar.gz
 # cd prizmcc_<version>_deb
 # sudo dpkg --force-depends –i *.deb
 'dpkg' does not resolve dependencies automatically, so please ignore possible errors, if you did not install required dependencies yet, and invoke next command
 # sudo apt-get –f install

Generic .tar.gz Distribution

We also provide a generic .tar.gz package. You will need to install the dependencies described in the Requirements section. Once the dependencies are installed, you can install the .tar.gz with the following commands as root:

Example
Copy Code 
# tar -xzvf prizm-contentconnect*.tar.gz
 # tar -xzvf prizm-services*.tar.gz
 # cp -R prizm /usr/share/

 

Step 3 - Configure

  1. Continuing as root, change to the installation location: /usr/share/prizm and run setup.sh. This will run the Prizm Licensing Utility (PLU) and configure PCC for its first run:

setup.sh launches the Prizm License Utility (PLU), which is a GUI application. Depending on how you have X11 configured, you might need to run 'xhost +' as the logged in user to allow the PLU launched by the root user to access X11. You can disable X11 access for root by executing 'xhost –' when you are done.
Example
Copy Code 
# ./setup.sh
Select the type of license you want to acquire:
                1) Evaluation [e]
                2) Deployment [d]
            Choose 1 or 2: d
            Select the type of deployment license you have:
                1) Node Locked [n]
                2) OEM         [o]
            Choose 1 or 2: o
            Provide the solution name: PCC9
            Provide the OEM license key provided to you: 2.0...
            Your deployment license was acquired successfully.
            ./scripts/pccis.sh start
            Starting Prizm Content Connect Information Services...
            Starting Nginx process...
            Starting PCCIS Watchdog process...
            PCCIS Watchdog has been started correctly.
  1. For a production installation, you will want to configure where log files are stored and ensure that Nginx logs are rotated and pruned. See the section How to Configure Log File Locations. 

 

Step 4 - Configure on CentOS 5.x (Optional)

If you aren't running CentOS 5.x, you can skip to Step 5 below.

PCC will not work on a CentOS 5.x system with the default LibreOffice. For this purpose you need to download and install LibreOffice from libreoffice.org as described below:

  1. Install the latest stable version of LibreOffice for your OS. Download and install it from this location: www.libreoffice.org/download
  2. Follow LibreOffice Installation instructions from this location: www.libreoffice.org/get-help/documentation/

LibreOffice Desktop Integration for Linux is not needed; you do not need to complete those steps.

The LibreOffice installation might fail if you have LibreOffice or any other application already listening on any of the following ports: 18580, 18584, 18585, 18586, 18590, 18591, 18592, 18593, 18680.

By default, Prizm Content Connect installs the proxy service on port 18680 and uses 3 of the following ports for conversion purposes: 18580, 18584, 18585, 18586, 18591, 18592, 18593. You can add more ports as your traffic increases.
  1. Locate root folder of your LibreOffice installation. The LibreOffice is usually located in the following directory: /opt/libreoffice4.x
  1. Edit <prizm-install>/conf/proxyserver_jar.properties and change following parameter to fit the root location of LibreOffice:
Example
Copy Code 
Office Document converter installation base directory
#odc_installation=/usr/share/prizm/libreoffice
odc_installation=/opt/libreoffice4.3
  1. Change the watchdog.config OCS officeInstallPath to point to a community version of LibreOffice:

By default this value is:

Example
Copy Code 
"officeInstallPath":"../libreoffice/program"

or

Example
Copy Code 
"officeInstallPath":"/usr/share/prizm/libreoffice/program"

Example of fixed path:

Example
Copy Code 
"officeInstallPath":"/opt/libreoffice4.4/program"
  1. Save proxyserver_jar.properties, restart Prizm service and check proxyserver.log to make sure PCC uses the installed LibreOffice. 

 

Step 5 - Verify that the Installation was Successful   

  1. Browse to the following either via URL or through browser http://localhost:18681/admin:
 
It may take several minutes for the Services to become completely healthy. The page will auto-refresh as the Services come online.
  1. Your installation is now complete.

Working with Sample Code

Sample code is included to demonstrate how Prizm Content Connect can be integrated into your Content Management solution. Sample applications using different languages are packaged with the product to demonstrate using a particular language. All of the product samples are located in the "Samples" folder within the installation directory. For more information, refer to the Code Samples topic.

How to Install Common Certificate Authority Root Certificates on Linux

The following commands should all be run as root. Additionally, if prompted for addition/removal permission, then yes/no should be entered as the response.

  1. Install all Mozilla's root certificates. This command will install all the root certificates Mozilla accepts, prompting only to remove certificates that Mozilla doesn't list, adding all it does trust without prompt. This should make HTTPS work for any system that Firefox works with:
Example
Copy Code 
/usr/share/prizm/mono/64/bin/mozroots --machine --import --ask-remove
  1. Pull certificates from an https connection to accept:
Example
Copy Code 
/usr/share/prizm/mono/64/bin/certmgr -ssl -m https://servertoadd/

As long as the server includes the entire chain to root, this will allow the certificate to authenticate. This will generally be the case for self-signed test certificates. For more complex situations, any required items from the chain will need to be added manually.

  1. Manually add the certificate from the file:
Example
Copy Code 
/usr/share/prizm/mono/64/bin/certmgr -add -c -m /path/to/certificatefile

The certificate stores the certificates at: /usr/share/.mono/certs/.

Enabling Upload of Larger Files Through nginx on Linux

By default /usr/share/prizm/nginx/nginx.conf contains the following limitation:

/usr/share/prizm/nginx/nginx.conf
http {client_max_body_size 100m; ... }

which limits maximum document file size to 100Mb, and so nginx will return HTTP-500 when larger files are uploaded to the service.

If you are dealing with larger files it will necessary to change "client_max_body_size" option to a more appropriate value.

 

 

©2015. Accusoft Corporation. All Rights Reserved.

Send Feedback